@niklasmohrin Looks like there have been some changes on main since this PR was created (partly my fault 😇). Most likely, there will be conflicts in the imports. Do you see a checkbox that "allow[s] edits by maintainers"? If so, I can rebase whenever this PR gets out-of-sync, if you like 🙂

I checked the box now, but actually I think I would prefer to just do the rebase myself, it's not too bad and gives me less anxiety than multiple people force pushing a branch :D

I will not work on this this weekend, so feel free to push as many conflicts as you want to main :) I will write a regex for the rebase

Haha, all right! I'll delay the import rewrites from #473 (comment) anyway, but good to hear that the rebasing won't be an issue for you 🙂

I updated the PR description with the current information and my thoughts on what to do next. I think I am happy with the current state of the PR. Let me know what you think about the PR and the proposed next steps.

When merging: Please squash everything :)

I'm also happy with the current state and the list of things to do after merging this PR, thanks a ton! 😄 ❤️

Because we have NWERC coming up (30 November), we'll wait with merging this until after that contest. Then we'll also have more time to do a thorough review 🙂 I'll keep using your branch during problem development to see if things break (so far, so good)! In the mean time, feel free to investigate some of the follow-ups if you have the time (also fine if you don't have the time) 😄